Section/item	List of significant changes
Chapter 0	Revised Chapter 0 General
Chapter 1	Revised Chapter 1 Management and Administration
Chapter 2	Revised Chapter 2 Logipad Modules
Chapter 3	Revised Chapter 3 EFB Approval Process
Chapter 4	Revised Chapter 4 Human Factor Mitigation
Chapter 5	Revised Chapter 5 EFB Principle Crew procedures
Chapter 6	Revised Chapter 6 EFB Training Program
Chapter 7 (Appendix)	Revised Chapter 7 Risk Assessment for Logipad Aero

PURPOSE OF MANUAL

The purpose of this Manual is to provide the organizational structure and specification, responsibilities, administrative and standard operating procedures and steps in the workflow of the Electronic Flight Bag (EFB) Program in a clear and comprehensive manner to end users:

Flight operation managers
Pilots;
Dispatchers;
Flight Operations Officer.
Ground personnel
Maintenance personnel, …
Operators Employees,…

The main objectives of this Manual are:

To define the functional responsibilities in order to ensure the clarity of roles, authority and accountability of all persons in charge of the EFB Program.
To establish the administrative and operating procedures within the scope of the EFB Program in order to maintain and improve the co-ordination capability, as well as the performance and stabilization of methods and models of operation which are used in the Program.
To provide the guidelines for regulating the activities within the Program in order to achieve the Program’s objectives in conformance with the Company interest.
To provide a detail on the training matters relating to the EFB Program.
It shall be noted that EFB program (include operating procedures, pertinent training modules, checklists, operations manuals, training manuals, maintenance programs, minimum equipment lists (MEL), other pertinent documents, and reporting procedures) was build incorporated into Operators policy.

ABBREVIATIONS

The following abbreviations may be used in Logipad manuals

A/C	Aircraft
AMC	Acceptable Means of Compliance
ARINC	Aeronautical Radio, Incorporated
OFP	Operation Flight Plan
PPS	Flight Planning System
PED	Portable Electronic Devices
MUI	Logipad Management User Interface
EASA	European Aviation Safety Agency
EFB	Electronic Flight Bag
EFF	Electronic Flight Folder
IATA	International Air Transport Association
ICAO	International Civil Aviation Organization
ORO	Organization Requirements for Air Operations
CAT	Commercial Air Transport
SPA	Special Approvals
NAA	National Aviation Authorities
NCC Non Commercial Complex	Non-Commercial Complex

DEFINITIONS

The following definitions are specific to this Manual and may differ from those definitions contained in other published references.

Administrative Control Process: Operator-administered procedures to control and record the EFB Program’s operations process
Portable EFB: Portable components supporting EFB applications are considered PEDs. For a PED to be considered an EFB, the PED must actively display Types A and/or B software application(s) (e.g., when a PED is displaying personal email, the PED is not considered an EFB; when the same PED is authorized and actively displaying a Type B aeronautical chart application, it is then considered an EFB).
Installed EFB: EFB equipment components supporting EFB applications are “installed” when they are incorporated into aircraft type design under 14 CFR part 21,AMC 20-25A or as a proper alteration under 14 CFR part 43, § 43.3.
Type A Software Applications: Have a failure condition classification considered to be no safety effect; Do not substitute for or replace any paper, system, or equipment required by airworthiness or operational regulations; and Do not require specific authorization for use (i.e., although the Type A EFB application is part of the operator’s EFB program, Type A EFB applications are not identified or controlled in the OpSpecs or Management Specifications (MSpecs)).
Type B Software Applications: Have a failure condition classification considered minor; May substitute or replace paper products of information required for dispatch or to be carried in the aircraft; May not substitute for or replace any installed equipment required by airworthiness or operating regulations; and require specific authorization for operational authorization for use (i.e., each Type B EFB application must be authorized by the FAA in
Miscellaneous (non-EFB) software applications: Miscellaneous software applications are non-EFB applications, supporting function(s) not directly related to operations conducted by the flight crew on the aircraft.
Critical Phases of Flight: Critical phases of flight in the case of aeroplanes means the take-off run, the take-off flight path, the final approach, the missed approach, the landing, including the landing roll, and any other phases of flight as determined by the pilot-in-command or commander.
Electronic Flight Bag (EFB): An EFB is any device, or combination of devices, actively displaying EFB applications. EFBs are characterized by the following: An EFB hosts applications, which are generally replacing conventional paper products and tools, traditionally carried in the pilot’s flight bag. EFB applications include natural extensions of traditional flight bag contents, such as replacing paper copies of weather with access to near-real-time weather information. In order to qualify as an EFB application, the failure effect must be considered a minor hazard or have no safety effect. Acceptable EFB applications are listed in section 1.2.2 These EFB applications may be overlaid or integrated. EFBs cannot replace any installed equipment required by operational or airworthiness regulations. EFB applications have no certification requirements for installation under aircraft type design.
Electronic Flight Folder (EFF): An EFF software contains flight plans, NOTAMS, weather charts, and additional flight information, for example, and the structure can be adapted as required. The look and structure of the Flight Folder can be aligned with the operations manual and briefing definition
Hosted Application: Software running on an EFB that is not installed or considered part of aircraft type design
Interactive Information: Information presented on the EFB that, via software applications, can be selected and rendered in a number of dynamic ways. This includes variables in the information presented based on data- oriented software algorithms, concepts of de-cluttering, and selectable composition as opposed to pre-composed information.
Mounted: Any portable device that is attached to a permanently installed mounting device
Mounting Device: A mounting device is an aircraft certified part which secures portable or installed EFB, or EFB system components.
Stowed : A portable device that is placed in a secure stowage location but is not available for use or view by the pilot in that location
User: means Pilots, Cabin Attendants, Dispatcher and Flight Operation Officer.
Company iPad: iPads which have been assign to individuals for their duty. Company iPads are certified as official devices to perform Operator’s EFB.
Personal iPad: iPads which are personal priorities,
Warranty time: 01 years starting from the date receiving a company iPad.
Viewable Stowage : A device that is secured on the flight crew (e.g. kneeboard) or in/to an existing aircraft part (e.g. suction cups) with the intended function to hold charts or to hold acceptable light mass portable devices (for example an EFB of no more than 1 Kg) viewable to the pilot at her/his required duty station. The device is not necessarily part of the certified aircraft configuration.

The term “must” is used to indicate mandatory requirements.

The terms “should” and “recommend” are used when guidance is recommended, but not required.

MANAGEMENT AND ADMINISTRATION

EFB SYSTEM OVERVIEW/ CONTROL AND RESPONSIBLE:

LOGIPAD EFB SYSTEM

The Logipad Aero EFB System consists of following elements;

HARDWARE CONSIDERATION :

Logipad solutions is a set of type B software which can be using for electronic devices. We recommended all airlines should using COTS (Commercial Off-The-Shelf) hardware already approved by EASA and FAA for use as EFB device.

The Hardware should compliance with the following standards: EASA AMC20-25 and FAA AC120-76C for:

Electromagnetic Interference (EMI) Demonstrations
Environmental Testing (Rapid Depressurization)
Batteries

According to the test, these iPads do not affect the performance of aircraft systems, equipment or the ability to operate the aircraft; EFB hardware should be consideration in the following items:
Paper Data Removal

Ideally, at least two operational EFBs would be needed to remove paper products that contain aeronautical charts, checklists, or other data required by the operating rules. The design of the EFB function is such that it would not allow for a single failure or common mode error may cause him loss of required aeronautical information.
Electrical Power Source

For EFB Hardware, The System design must take into account the source of electrical power, the independence of the power sources for multiple EFBs, and the potential need for an independent battery source. Battery-powered EFBs that have aircraft power available for recharging the EFB battery are considered to have a suitable backup power source. EFBs that do not have a battery power source and that are used in place of paper products required by the operating rules must have at least one EFB connected to an aircraft power bus.
The replacement of Battery

In the event that a battery is designed with the option of replacement, the established guidelines for battery replacement interval, as specified by the manufacturer of the original battery (or cell), should be observed. In instances where the manufacturer of the original battery (or cell) has not provided a specified replacement interval, the guidelines established by the manufacturer of the replaceable battery should be adhered to.
Battery Backup:

Consider equipping the EFB PED with an alternate power supply to help achieve an acceptable level of safety. For EFBs without an aircraft power source, it's possible that a backup battery might be needed. In addition, backup batteries are required to comply with established lithium battery safety and testing standards concerning fire prevention, environmental testing, and performance testing, . These standards are implemented to ensure that the battery is adequately capable of functioning within the aircraft and fully compliance required of CAAs. The operator should also make sure that batteries are replaced as required, at least as often as the EFB manufacturer's recommended interval.

EFB MOUNTING DEVICES :

Logipad is an application and does not require specific mounting device requirements. However, operators should ensure that the mounting devices fully comply with the hardware devices used for the organization and are fully compliant with the requirements of all civil aviation authorities for safety operations.

SOFTWARE/ EFB SYSTEM CONSIDERATION :

Software Classification: EFB solution is a comprehensive of flight briefing applications, documentation, E-Form, which allow pilots to access their flight package on board the aircraft and also from home/ hotel/crew room via internet connection that replaces day of flight paper documentation. These applications meet all the requirements set by EASA/FAA in AMC 20-25/FAA AC 120-76D for use as EFB Type B software

CONTROL AND RESPOSIBILITIES.

The Administration section of this system encompasses all individuals involved, the organizational structure and processes, and the administrative applications utilized for automating control processes. The following groups of people are proposed to interact with the system to enhance its effectiveness.

Head of Flight Operations / Director of Flight Operations

The Head of Flight Operations (HOFO) or Director of Flight Operations (DFO) bears the overarching responsibility for all flight operations conducted under their Air Operator Certificate (AOC). This responsibility encompasses ensuring the safety and compliance of flight operations with aviation regulations, as well as overseeing the EFB system. The HOFO/ DFO reports directly to the Accountable Manager for all flight ops status
EFB Program Manager

The EFB Program Manager oversees the system's operation and manages the lifecycle of EFB applications, from development to release, including testing protocols, version upgrades, deployment strategy, and communications plans. The EFB Program Manager oversees the system's operation and manages the lifecycle of EFB applications, from development to release, including testing protocols, version upgrades, deployment strategy, and communications plans. The operational structure of the operators dictates the position's independence or integration into the responsibilities of the Technical Office Manager or Chief Pilot.
EFB Administrator/ Operations Engineer

The EFB Administrator/ Operations Engineer is responsible for managing the Logipad Portal and configuring the server parameters to align with Operator field. Upon receiving a flight package and documentation data, the EFB Administrator will update the database on a gateway and notify all users to update their iPads accordingly. Logipad’s dynamic admin portal (MUI, Flight Manager, Jasper report server) has been created to assist with administrative tasks. Logipad Team also provided 24/7 Support Center for all client’s tickets.

Management User Interface (MUI) Over view :

The Logipad Management User Interface (MUI) provides web services for retrieving and releasing user data, EFB data (including target associations, properties, metrics, and configuration data), and automation services for performing synchronous tasks for Operators. Furthermore, it assigns and deploys the user's data to users and devices, regardless of the hardware used (iOS, Windows, or Android devices).

The main functions for MUI shall be listed as bellow:

User management
Create news
Provide documents
Deploy e-Forms
Retrieving the completed e-Forms
User reports and statistics

The user management system is based on a user/role framework, which is customizable to suit the needs of individual users. Content access and permissions are determined based on the user's assigned role.

The Management User Interface also called « MUI ». is a web-based interface.

When accessing the website, a login window appears, where the user must enter his login name and password.

Depending on the Operator’s `configuration the local login or the login with a Directory service is possible

After successful login you will get to the start page of MUI

General section :

Users/ Add Users :

To add a User to the system click on the button Create a new user to open the dialog with the user settings. To edit an existing user click on the edit button

To delete an existing user press the delete button

The user dialog hat the following fileds :

Login name

The login name for the user. This is the only mandatory field
Full name
eMail

3LC

Three letter code
Type

User type. This field is just used to organize the users. The select will automatically add new values
Department

User department. The select will automatically add new values
Content role

Role member ship for content assignment
Access groups

Membership in Logipad security groups. For normal users the default values are ok
Reportable

User should be listed in reports. Useful to exclude test accounts
Active

Only ‘active’ users are able to login
Description

Exporting and importing users :

The user has also the option to export users or to perform a bulk import

By pressing the « Arrow down » button on the right side of the button you can access the additional function.

Exporting users :

The user export has only the option to choose the seperator and the escaping. Result will be a CSV file.

Importing users :

The user import needs a separator and escaping for the file and needs a CSV file as input. The following

fields could be used. Only the login name is mandatory:

• Name

• Type

• FullName

• Email

• ThreeLc

• Department

• Description

• IsActive

• IsReportable

• Roles

The roles need to be separated by a ‘,’.

Content Roles :

The second point in the general section is the management of content roles.

Create a content role

The creation of a content role can be done by clicking the button Create newcontent role and assign the role name and type. The type is optional.

Edit or delete a content role

You can delete a content role by clicking the delete button Edit will be start with the edit button

Changing the user assignment to the role

The role assignment dialog will be visible after clicking on the small arrow at the beginning of the row.

You can remove the member from the role by clicking

After using the button Add Users to content role you will get an additional dialog to add users.

Notification

The last entry in the general section is used to create and monitor notifications.

Important:

After the message was created it cannot be changed.

Creating a notification

A notification can include:

• Title

• Message

• Reference to Documents eForm, News or Weblink

and can be assigned to

• Users

• Content Roles

EFB Approval Process Guidance :

Pre- Application Phase: The first phase starts when an organization or individual inquiries about or states a need for a change in some aspect of an aviation activity.
Initial Application Review Phase: The 2 nd phase starts when the applicant formally applies package for the Project evaluation
Document Conformance Phase: This phase commences when the aviation authorities (NAAs) review, analyze, and evaluate the application package. The NAAs may require a test session, compliance matrix/reports or risk assessment if deemed necessary.
Inspection & Demonstration Phase: During this phase, the NAAA will finalize plans to inspect and evaluate the applicant's demonstration of their ability to perform in accordance with the formal application package's procedures, guidelines, and parameters. The NAAs can perform inspections and observe the applicant's demonstration through test sessions, tabletop exercises, ramp inspection programs, and other means.
Final Certification Phase. On this phase the Local Aviation Authority/ National Aviation Authorities (NAAs) finalizes by approval or acceptance by certificates, ops spec for the applicant. If the application is not approval or accepted, the applicant will be notice in phase 3 or 4

Flight manager - simple to use, control and export of flight data

Flight Manager- Overview:

The Flight Manager platform provides web services to view, select, generate, control and export flight related data including fuel logs, briefing attachment files, flight logs and briefing definitions for daily flight operations. In addition, you can view a list of previously created, activated and completed flights in the operation history

Briefing section / management, and generate/ upload all flights by status

View all flights in a given period by status. Select the flight status (Prod, Test) and the status (Created, Activated, Finalized). Created means the Briefing Package has been created, activated means the Briefing Package is active and ready, and Finalized means all crew have completed and returned the Briefing Package

View all/ View Finalized/ View released.; View all flights in a given period by status. Select the flight status (Prod, Test) and the status (Created, Activated, Finalized). Created means the Briefing Package has been created, activated means the Briefing Package is active and ready, and Finalized means all crew have completed and returned the Briefing Package

Dynamic table: You can quickly search and find the flight you want using a table with filters. The following but not limited filter apply for the table

Departure IATA code (3- Letter)
Departure ICAO code (3- Letter)
Arrival IATA code (3- Letter)
Arrival IATA code (4- Letter)
Flight (Flight number)
Aircraft (Aircraft registration)
Master user (Pilot in command user)
Departure time (The time when Actived the fight)
State (Prod/Test)
Status (Created/ Activated/ Finalized)

To see detail of the flight, select , To see all the figure of the flight select , to Download all attached files select , In additional is also able to display the briefing details or download the briefing, The dispatcher can make changes or see the crew composition for the fight in the Assignment sheet

New briefing: The function allows you to manually create a new briefing package by selecting the correct Flight Planning System (.EFF) file and creating a briefing with your attachment files such as fuel receipts, ground reports and METAR/TAF. The crews for the flight have been selected by creating and simply releasing the flights.

Import from PPS: Automatically import and generate multiple flights directly from Flight Planning system from API connection. The crews for multiple flights have been selected by creating and simply releasing the flights

Attachment Types: All attachment of the flights can be selected within briefing manager, Easy control and management

Definitions section: The section allows you can select, define and assign the layout ( Colour, Texts, Placement of content…) which you want apply for your package

Logipad Webclient

Logipad Webclient is a software application that facilitates access to and display of module form and document content through a web browser. It functions as an intermediary between users and web servers, enabling users to interact with websites, view multimedia content, support digital formats, and access various online services.

Logipad user interface :

After Sign in to Logipad Identity System ( Keycloak), you will see home screen of Web client version. In addition, users have the option of accessing a content summary of the number of documents, electronic forms, and web addresses linked to Logipad. A list of news about the EFB system and acknowledgment button is also available. Logipad web client are available for all Operators users

Logipad Documents module :

Documentation support for the following functions:

Docs View Section: Select search option for documents using by

Folder View
Total Documents
Number of Docs need confirmed

Docs View Filter: selectively filter documents by:

Name
Creation Date,
Document Priority
Document Confirmation Request Date

Document Properties Section:

In this section, you will find the options for each document in the laptop format. These include the following:

document creation date,
document editing date,
document folder path,
document version number,
option to open document in another window,
document request date,
vertical priority color bar.
Confirmed section

Document in view option:

Logipad Eforms Module :

Eforms Template/ History Section :

This section allows you to select pre-made and initialized templates as well as to fill out and submit your own report forms. Additionally, the History section allows users to review previous transmissions and generate electronic reports.

Document View Editing:

With the report correction section. You can edit, fill in the information for the report directly on a web browser, Save the draft, as well as cancel and submit the report

Show/Hide Eform Option:

Logipad App Center

This section contains the versions of the software that are compatible with different platforms. It also includes QR templates that can be used to download settings and install applications. Additionally, it features modules that are currently under development by Logipad. All Logipad future modules will be integrated into versions of the software that are compatible with each individual platforming an appropriate way.

Jasper report/ Logipad reporting server

The Jasper Report Library is an open-source reporting engine for Logipad data regarding users, documents, briefings, and EFF data, as well as eForm reports. The Jasper Reporting Engine is entirely written in Java and is capable of utilizing data from any type of data source to produce pixel-perfect documents. These documents can be viewed, printed, or exported in a variety of document formats, including HTML, PDF, Excel, OpenOffice, MS Word, CSV, and others.

Administration Folder

This folder contains a list of users categorized according to their access rights, thereby enabling the user to easily control statistics and edit access rights based on visualized report data.

Access Group Memberships

This folder contains a list of users categorized according to their access rights, thereby enabling the user to easily control statistics and edit access rights based on visualized report data.

Report files could be export under:

PDF
CSV
DOCx
RTF
ODT
ODS
XLSX
PPTX
CSV
Excel Metadata

Active Report Server

The active report server is utilized for the purpose of monitoring the overall status of users who utilize the software. The following information is employed in the following items bellow:

Deactivated
Excluded
Reportable
Active
Last active time
Last Sync time

User reports :

For user reports folder, you could be able to see and analytics status report for each users or list of missing confirmation by user

Confirmation missing by user:

Briefing Report Server :

This folder contains two types of information regarding flights: one type is an overview of flights that have been released, and the other type is a list of flights (briefing package) that have not yet been finalized. The purpose of this folder is to facilitate the identification of the cause of any discrepancies.

Not finalized briefing :

The list of flights has not yet been finalized. The person in charge of flight operations (i.e., the "master user") has not yet completed the list. The release will be compiled according to the city pair, time, package status, revision

Release Briefings :

In the release briefing section, each element of the list of flights created from flight planning data over a specified time period is displayed. To access the list, users are required to select the desired time period to initiate the search process. The system will then generate a list of corresponding flights, as well as a list of master users, a list of users, and a list of download times.

Document Reports

The document folder has been developed to facilitate the extraction and analysis of reports according to the following criteria:

All documents: This function is employed to summarize all documents, encompassing assignments, downloads, and read confirmations.
Confirmation by role: This feature enables the visualization of documents that have been confirmed by each role.
Documents report: This report provides a comprehensive overview of specific documents.
Documents by role: This report illustrates all documents that have been assigned to a particular role.

All Documents Folder:

Confirmation by role:

Document report:

Documents by role:

LOGIPAD MODULES

OVERVIEW :

Logipad Solution including the followings 3 modules:

Documentation module: The airline's document management system enables users to display, manage, mark documents with priorities assigned, provision documents to content roles, make remarks for various types of documents (PDFs, XMLs, WORDs,…), and distribute operational documentation. The operational documentation includes both manufacture and operator manuals.

Briefing Module: The electronic briefing system provides pilots with a series of folders containing essential information such as the Operational Flight Plan (OFP), weather updates, Notice to Airmen (NOTAM), Loadsheet information, NOTOC and any additional details required. The system has a flexible layout and structure to ensure that all information is presented in a clear and logical manner.

Eform module: The Digital Forms solution allows you to create your own electronic forms in an intuitive and logical way using a drag-and-drop editor or by using existing templates. The modules can be used for web services, IOS devices and direct synchronization between different devices and platforms, increasing the efficiency of air-to-ground communication management.

DOCUMENTATION MODULE :

One of the central points of Logipad is the management and role based provisioning of documents.

Documents can be additionally equipped with further attributes to extend their organization. Available functions:

• Provision documents to content roles

• Mark documents with flags

– Confirmable

– Exportable

– Indexable

• Priorities for documents can be assigned

• Control whether the documents should be opened in the app or in an external application

• Control unit to publish the documents time-controlled. “Valid from:” and “Valid until:” fields.

• Comment function for the internal description

• Control to turn on the inventory when opening the document

The system allows the publishing of different content types like:

• video

• txt

• epub

• zip

• pd

• video

• txt

• epub

• zip

• pdf

• htmlzip

• html

• doc

• docx

• xls

• xlsx

• ppt

• pptx

Organize documents

Documents are organized in a folder structure. A Folder can be associated with a document template to assign standard properties.

The two icons at the top right-hand side activate the Folder View or the Document View.

Folder view

Will show the folder structure with subfolders and files.
- Document view
  
  display all documents (including documents within subfolders).

Document templates

Document templates define a set of properties/settings that later will automatically be applied to new documents.

The first button Create new Document is a dropdown select button. The standard selection is Create new Document. Other options are:

• Upload multiple documents

• Document Types

• Document Templates

If Document Templates is selected, a Document Template is created to associate default properties once a document is assigned to that template

Create Folder

The main attribute of the folder is the Display Name additionally a document template can be assigned.

If you don’t assign a template the folder will inherit the template of the parent folder. Access Rules are used to limit administrative access.

Publish a single document

A document has two sections of attributes:

• Document attributes

– Display Name

– Folder

– Content Roles

– Document Type

– State

– Document Priority

– Confirmable

Only if ‘Confirmable’ is activated the ‘read confirmation required’ will be activated on the

version.

– Indexable

Included in fulltext index.

– Exportable

User can print the document and export it to other apps.

– Open in External App

• Version attributes

– Revision

– Is visible

– Valid from

– Valid To

– Comment

– Require read confirmation

Publisher multiple documents

You can select the document with a file dialog or use “Drag and drop”.

During the upload you can only assign some attributes.

• Folder

The default folder for the upload is where you started the dialog.

• Use folder template

Should an existing template be applied

• Comment

• State

BRIEFING MODULE :

The Electronic Flight Folder contains flight plans, NOTAMs, weather charts and additional flight information, structured according to our customer's operational manual and briefing definition and fully compliant with the ARINC 633-2 standard. Briefing data can be exchanged between multiple devices and platforms. The management of your data can also be customized, such as fuel consumption data and the corresponding prices stored in the backend. The data can be transferred to other systems, such as for fuel optimization. Additional information can be collected via separate sections or self-built eForms.

User interface layout :

Logipad Navigation bar are implemented in the following section :

Home Screen:

General update, Review Updated information and notification section for all modules

Briefing section

The data transmitted to your EFB application and into the Logipad app is called a Briefing. A Briefing contains all flight scheduling data, such as aircraft status, flight plan information, and weather charts. The Briefing section allows you to activate, finalize and collect all flight relevant data. It also ensures real-time updates between crews.

Briefing info and standards layout concept

Briefing Info

This is the Briefing main page, here you can find an overview of the active Leg and navigate the different flight phase modules:

Flight summary (Basic Trip summary info)
OFP
Weather & NOTAMs
Weather Charts
Flight Data
Additional Documents

Flight Summary

The section contains General info of OFP from Flight Planning system source regarding to the following topic:

Flight Scheduling Data (Date & Time, Date, A/C registration)
Flight Planning Data
Document/ Crew Infor
Flight release acceptance and remark

Weather & NOTAMs

The section in Briefing Package contains all information from Operator weather data source (PPS system or Independent sources) . All information have been handle and transfer with Logipad MUI platform which generates to general Briefing package (ARINC format compliance)

Airport Weather : ( Destination, Departure and Alternate Airport ) METAR & TAF reports
Wx Charts (Different charts / SIG / Winds Aloft / etc., as planned)

Flight Data

The section in Briefing Package contains all information for dispatch, monitor the progress the flight and all relevant data as Operator’s Layout (Alternate Route, Plotting Chart, ATC Flight Plan, Fuel & Mass) regarding the following section:

Pre- Flight
In- Flight
Post- Flight

Additional Documents

This section is used to provide additional documents previously received in paper format (Permit docs, Loadsheet, NOTOC,Paper Flight Plan…)

Data Entry Field/ What need to know ?

Logipad EFB solution using a set of different entry field in order to support users while using App.

Mandatory Entry Field :

Entry fields with a red frame are mandatory fields and must contain a value before the briefing can be processed
Optional Entry Field :

Entry fields with a green frame are optional fields and contain a references information for the flight
Data Entry Format Restriction :

Whenever you see a data entry format like DD.MM.YY or hh:mm you must followed the format to entry into the field

Briefing package / Activated and transfer data during the flight

How to active a Briefing.

Before you can enter and modify data inside a Briefing, the Briefing needs to be activated. Activation can be done by the Master User or by the Non-Master User. After activation, the Briefing icon is green coloured.

Role: Master User

This is the user responsible to finalize and send the completed Briefing. In general, the PIC is assigned to the “Master User” role. The crown above the briefing icon indicates the assigned “Master User” role.

Role: Non- Master Use

The “Non-Master” user does not own a crown. In general, the F/O is assigned to the “Non-Master” role and cannot “finalize” a Briefing

The Master-User and Non-Master User concept assures that only complete data collected from both devices are sent to the server (single channel concept)

To Activate a Briefing as a Master User (Briefing icon with Crow icon)

First press on “Briefings” in the Navigation Bar to see the relevant briefings assigned to you
Then, on the relevant Briefing, press on the three little dots on the right-hand side and press “Activate master copy”
Press “Activate” and observe the briefing Icon status change from yellow “ready” to green “active”

How to active a Briefing as a non-Master User (briefing Icon without Crow)

First press on “Briefings” in the Navigation Bar to see the relevant briefings assigned to you
Then, on the relevant Briefing, press on the three little dots on the right-hand side and press “Activate non master copy”

Press “Activate” and observe the briefing Icon status change from yellow “ready” to green “active”

Important

If the Non-Master User is activating the Briefing, and does all the entries for the trip, then he/she must transfer the briefing to the Master-User Device at the end of the flight, in order to perform the “finalization” of the Briefing. Only the Master-User can finalize and send a briefing.

Roll Back Briefing Activation

If for any reason you need to roll back a briefing activation (activation of the wrong flight or troubleshooting), here you can find the necessary steps to do so.

Press the information icon to see the briefing properties
Press the energy icon to see the briefing Actions
Press ‘’Roll back activation’’ button
Confirm and check that the briefing status reverts to the yellow “ready” state

Real time Sync and Data exchanged

Logipad automatically detects all other devices nearby. Logipad selects the best possible available connection (Bluetooth, Access Point, or Wi-Fi Direct) and establishes a connection in the background, automatically synchronizing data in real-time which is entered by pilots. You can save times and effort for flight operation between Master user and Non-Master user accounts. In addition to connectors, we have developed easy-to-use functions to transfer data to other applications. Performance data from other applications can be imported into Logipad or vice versa. You can exchange data with other applications, provided this is supported by third-party vendors. The steps to steps

For the briefing active data exchanged betwen crews, the connection between the two devices must been established.

Press the communication icon in the sending data devices

Press accept on the receiving device

A successfully established connection is indicated by a green band on both devices.
To get the transfer option press on the three dots

To hand over the “active briefing” and, therefore, make it possible for your colleague to enter data (e.g. for a flight log, RVSM checklist & fuel entry), press here
To back up data on the other device (e.g. after a waypoint check), press here (only data is sent to the other device, the activation of the briefing remains on your device)
“Failover copy” is the new status of the briefing that remains on your EFB after transferring the “active briefing” to another device. This is a redundant copy with the data stored before transferring the “active briefing” to your colleague’s EFB. The “failover copy” can be activated in case the “active briefing on the other device becomes corrupted or if there is a hardware failure.

IMPORTANT: When an active briefing is transmitted, the briefing on the sending device (“failover copy”), becomes “read only” and the briefing on the receiving EFB becomes “active”, and is the only briefing that can accept crew inputs.

If the Non-Master User is activating the Briefing, and does all the entries for the trip, then he/she must transfer the briefing to the Master-User Device at the end of the flight, in order to perform the “finalization” of the Briefing. Only the Master-User can finalize and send a briefing.

Force Failover Function/ Transfer role between devices for abnormal operation

If the sending devices ( non-master users) unbale to transfer briefingd data due to connection, you can using the “Force Failover” function. This function allows the “Non-Master User” to become the “Master User” and therefore, finalize and send the Briefing. In order to do so please follow the steps to steps as bellow:

Tap “ information” icon for briefing properties

Tap ‘’enery ‘’ icon for Briefing actions
Tap “ Force failover” button

EFORMS MODULE :

Overview :

The Digital Forms solution allows you to create your own electronic forms in an intuitive and logical way using a drag-and-drop editor or by using existing templates

Logipad offers 3 subsidinary applications to for generated E- Forms templated, Data entry field in the template and send, Data collection and analysis as followed:

E- Forms Generator (Creating the operational form templated by your own)
E-Form Modules (To view, Entry field in and send Operational Forms when needed)
Report view dashboard (For post flight reports data collection)

eForm Generator :

The Digital Forms solution allows users to easily and intuitively create custom electronic forms using either a drag-and-drop editor or pre-existing templates. The tools working in Computer tools and direct sync with Eform modules in EFB devices for templated updated.

General ERP function :

With the General section you are able to see total existing Eform template on Logipad System, retrieve previous erp templated and re-updated in case you need modified, dowload erp, export files and erp template or created your new template
Editable function :

With Editable function you can able start to create your operation digital templated by your own requirement with out Coding. Our dynamics field have been deploy to support for you.

The dynamic field have been set in 4 different fields with different purposes :
Layout- Created Section, Row for Eform
Input control- Created text area, time & date picker, select and input
Buttons – Created buttons for Radio and Checkbox
Views- Created table, Dynamic table, Navtab,..
------- Created support field for Draw, picture attached or Signature signed

eForms Calculations :

The Editable function allows you to easily select the calculation method and field you want, and the result will be updated accordingly.

The eForms module offers several subfunctions for calculations :

Time Difference for effortless time conversion and calculation,
Date Time Difference for calculating the duration between two dates,
Number Sum for easily summing numbers without a traditional calculator,.
Number Difference : Subtraction the number easily without tradition calculator

EFB APPROVAL PROCESS

EFB Approval Process Guidance for Operator :

The Operator must obtain approval from their Local Aviation Authority/ National Aviation Authorities (NAAs) before officially using Logipad products for daily flight operations. The approval and certification process depend entirely on the authorities ‘requirements’ however the policies aligns with ICAO DOC 10020 (Manual of Electronic Flight Bags) which states that operational evaluation and approval is only required for commercial air transport operators. The same policy applies to EASA Part Implementing rules of Annex IV,V,VI and VII also referred to as :

Part ORO (annex III Organisation Requirements for Air Operations)
- Part CAT (annex IV Commercial Air Transport)
  - Part SPA (annex V Special Approvals – EFB)
  - Part NCC (annex VI Non Commercial Complex)
    
    However, the general EFB system approval process should include the following main steps:
Pre- Application Phase: The first phase starts when an organization or individual inquiries about or states a need for a change in some aspect of an aviation activity.
Initial Application Review Phase: The 2 nd phase starts when the applicant formally applies package for the Project evaluation
Document Conformance Phase: This phase commences when the aviation authorities (NAAs) review, analyze, and evaluate the application package. The NAAs may require a test session, compliance matrix/reports or risk assessment if deemed necessary.
Inspection & Demonstration Phase: During this phase, the NAAA will finalize plans to inspect and evaluate the applicant's demonstration of their ability to perform in accordance with the formal application package's procedures, guidelines, and parameters. The NAAs can perform inspections and observe the applicant's demonstration through test sessions, tabletop exercises, ramp inspection programs, and other means.
Final Certification Phase. On this phase the Local Aviation Authority/ National Aviation Authorities (NAAs) finalizes by approval or acceptance by certificates, ops spec for the applicant. If the application is not approval or accepted, the applicant will be notice in phase 3 or 4

HUMAN FACTOR MITIGATION

General :

The operator should carry out an assessment of the human-machine interface and aspects governing crew coordination when using the EFB. Whenever possible, the EFB user interface philosophy should be consistent (but not necessarily identical) with the flight deck design philosophy. The review of the complete system should include but not limited to:

General considerations including workload, usability, integration of the EFB into the flight deck, display and lighting issues, system shutdown, and system failures;
Physical placement issues, including stowage area, use of unsecured EFBs, design and placement of mounting devices;
Considerations for interference with anthropometric constraints, cockpit ventilation, and speaker sound;
Training and procedures considerations, including training on using EFB applications, EFB policy and procedures manual, fidelity of EFB training device, and mechanisms for gathering user feedback on EFB use;
Hardware considerations;
Software considerations

EFB PRINCIPLE CREW PROCEDURES

General

The operator should have procedures for using the EFB in conjunction with the other flight deck equipment. The procedures should adress and focust on the following topics :

Which information source will be primary;
Which source will be used as secondary information;
Under what conditions to use the secondary source; and
What actions to take when information provided by an EFB does not agree with that from other flight deck sources, or, if more than one EFB is used, when one EFB disagrees with another.

The Operators should include the requirements for EFB availability in the Operations Manual and/or as part of the minimum equipment list.

Flight crews should not have to confirm the revision dates for other databases that would not adversely affect flight operations in case of outdated data. Procedures should specify what actions to take if the software applications or databases loaded on the EFB are out-of-date.

Workload and Coordination

In general, using an EFB should not increase crew’s workload during critical phases of flight. For other flight phases, crew operating procedures should be designed to mitigate and/or control additional workload created by using an EFB.

Crews Workload should be distributed between flight crew members to ensure ease of use and continued monitoring of other flight crew functions and aircraft equipment. The procedures should include specification of the phases of flight at which the flight crew may not use the EFB, if applicable.

Reporting

A reporting system for EFB failures should be established. Procedures should be in place to inform maintenance and flight crews about a fault or failure of the EFB, including actions to isolate it until corrective action is taken.

Recommendation practice for EFB admin procedures

Data Generation and Validation before generated package

The EFB Administrator validates the data and flight plan data with Flight Dispatch Team, ensuring that it is complete, correct, and traceable. This includes verifying performance data, weather, NOTAMs, and any other relevant information which integrated with Logipad system

Ensure that the release is sent to the Test Server prior to publishing:

Prior to updating the prod environment, the EFB Administrator publishes the new data on a test server first. This step allows for testing and minimizes operational risk in case of errors.

The system should log all updates to ensure traceability in the event of discrepancies.

EFB Notification and Testing:

The EFB Administrator has informed the EFB Manager that new data is available on the backup server for validation. The EFB Manager or responsible parties should verify that all data are correct and current.

Once the EFB Manager confirms that the data is satisfactory, the EFB Administrator will publish the final data and release the EFB notification to all users. This notification will include a summary of the update information in each time release, the version number, and other pertinent details to ensure that flight data is always current.

If the data is unsatisfactory, it is sent back to the EFB Administrator for update new revision

The EFB Administrator continuously monitors synchronization through the Flight Manager portal, MUI to ensure that all end-users (flight crew, dispatch) update their devices. Any discrepancies must be addressed immediately.

Back-up system :

Ensure a reliable backup system is in place for both the back-up server and manual processes (e.g., printed documents) in case of an EFB or system outage. This provides a fallback mechanism for dispatchers and flight crews to access critical flight data.

Recommendation practice for Flight Crew procedures

Pre- Flight Preparation :

Flight crews must synchronize their EFBs and cross-check with the EFB Notification, EFB New Data Package to ensure they have the latest data, including flight plans, weather updates, and ARINC 633 briefing packages. For Briefing Package. The crew team should always check the flight ID, master user information, city pair, with their roster schedule to ensure that they received the correct package from the flight planning system.

In Flight updates :

During flight, it is the responsibility of the crew to gather and record any deviations from the planned flight path, performance, or weather conditions. This data is then entered into the EFF system or documented. The crew should cross-check with the flight checklist to ensure that no information has been missed. The master user is responsible for final checking and releasing the package when all information has been filled in.

Post Flight Synchronization :

Following the flight, the crews will synchronize their EFBs with the Logipad server once more. This will ensure that all flights have been sent successfully for briefing and that the Eform has been released from Outlook. If necessary, the Eform will be resent. Consult with the EFB team to verify that all pertinent information regarding their duties has been thoroughly reviewed.

Recommendation practice for OCC/ Flight Dispatch procedures

Pre- Flight Preparation :

Flight dispatchers utilize the Flight Manager portal to prepare, verify, and manually dispatch flight packages to the crew. These packages include flight plans, NOTAMs, and performance data as required. Dispatchers must verify the accuracy of the data and coordinate with the EFB team to ensure that the crew has synchronized their devices prior to departure.

In- Flight Monitoring :

Dispatchers are responsible for continuously monitoring flight progress through the Flight Manager portal with the EFB team in real time. They are also responsible for communicating any necessary changes to the crew, especially in cases of weather updates or route adjustments that require updated flight packages

Post – Flight Data collection :

The dispatcher will coordinate with the EFB team to verify that all Logipad data is current and stored in the server. The data is stored in the central system and backed up to ensure full traceability for future auditing or operational review.

EFB TRAINING PROGRAM

EFB Training guidance :

The use of the EFB should be conditional on appropriate training. Training should be in accordance with the operator’s SOP (including abnormal procedures) and should include:

An overview of the system architecture;

Pre-flight checks of the system;

Limitations of the system ;

The use of each operational software application;

Restrictions on the use of the system, including when some or all of the EFB functions are not available;

The conditions (including phases of flight) under which the EFB may not be used;

Procedures for cross-checking data entry and computed information;

Human performance considerations on the use of the EFB;

Additional training for new applications, new features of current applications, or changes to the hardware configuration;

Recurrent training and proficiency checks; and

Any area of special emphasis raised during the EFB evaluation with the authority

Logipad Type of Certificates/ Training Syllabus

Logipad is responsible for training and providing EFB system administration training certificates for administrators and software usage training for operator instructors (Validate via question bank). The certificate is valid for 2 years and requires refresher training after 2 years. Operators' internal instructor will be responsible for training and renewal of certificates with guaranteed minimum participation time in Logipad's training syllabus content.

Logipad Training Syllabus

Subject	Time	Pass / Fail	Comment
Logipad Administrator Training Course- EFB admin instructor
Manager user interface (MUI)	4 Hours	Pass Fail
Flight Manager	4 Hours	Pass Fail
Jasper Libary Report	2 Hours	Pass Fail
Eform generator Tool	4 Hours	Pass Fail
Logipad Aero User Training Course - Using for Airline instructor
Documentation	2 Hours	Pass Fail	Apply for all certificate
Eforms	2 Hours	Pass Fail	Apply for all certificate
Briefing	5 Hours	Pass Fail	Apply for all certificate
Webclient	1 Hours	Pass Fail	Apply for all certificate

Type of certificates

Logipad Administrator Training Course- EFB admin instructor

Logipad Aero User Training Course - Using for Airline instructor

RISK ASSESSMENT FOR LOGIPAD AERO FUNCTIONS

RISK ASSESSMENT FOR LOGIPAD DOCUMENTATION MODULE

This section provides the risks assessment for the use of the Documentation module that is part of the Logipad with Dextra Data software suite.

The objective of this risks assessment is to demonstrate that the application achieves at least the same level of integrity and availability as the “traditional” paper means

Failure Cases and Mitigation Means

Types of risks are looked at and their consequences defined and mitigated. They are:

Total loss of the application
Data corruption
Undetected false output from the application.

Mitigation means are processes and procedures defined to compensate each identified failure case. They are means to provide availability of the application and to ensure detection of a false output.

Table 1: Failure cases and Mitigation means in Documentation module

FAILURE CASES	MITIGATION MEANS
When updating documents using the same name, the operation manuals are not correctly updated. Unable to access the latest version of Documents.	Logipad has an offline functionality. Previous documents ver-sions will be available. PDF expert/ One drive can be used as backup option
Long time for downloaded content	The content dowload size can be huge for the first syn-chronization. Therefore, ensure that a good and stable wifi connection is available. Logipad will only doing partial updates for all other synchronization EFB admin can mark documents for dowload only when wifi connecttion availlable
Erroneous Documents output Sometimes Documents are visible to users even if expired/ Documents are not visible to users even validity date is set Document’s confirmation cannot be set	EFB admin need to setting a new expiration/validity date and need to initiate a new release to productive. Logipad is operates in offline mode. Once a connection is establised the confirmation is automatically sent for users PDF expert/One drive can be used as backup option

RISK ASSESSMENT FOR LOGIPAD electronic Flight Folder ( EFF) MODULE

This section provides the risks assessment for the use of the Documentation module that is part of the Logipad with Dextra Data software suite.

The objective of this risks assessment is to demonstrate that the application achieves at least the same level of integrity and availability as the “traditional” paper means

Failure Cases and Mitigation Means

Types of risks are looked at and their consequences defined and mitigated. They are:

Total loss of the application
Data Corruption
Sent function was lost

Mitigation means are processes and procedures defined to compensate each identified failure case. They are means to provide availability of the application and to ensure detection of a false output.

Table 2: Failure cases and Mitigation means in EFF module

FAILURE CASES	MITIGATION MEANS
Briefing package is not syn-chronized to client.	Users Re-install and sync again, EFB admin do hash checking Sharepoint folder/ paper flight plan can be as backup method
Briefing package gets cor-rupted during synchroniza-tion from Backend System.	Users Re-install and sync again, EFB admin do hash checking Logipad offers a copy function to copy existing Briefing Pack-ages from crew members related to the same flight.
Filled eBriefing Package can-not be sent.	When Users filled eBriefings cannot be sent to the Logipad Backend System They will be stored on the device (Offline Mode). Logipad will automatically resent the filled eBriefing package once a connection (WIFI, 4G, LTE, 5G) is available.

RISK ASSESSMENT FOR electronic Forms (eForms) MODULE

This section provides the risks assessment for the use of the eForms module that is part of the Logipad with Dextra Data software suite.

The objective of this risks assessment is to demonstrate that the application achieves at least the same level of integrity and availability as the “traditional” paper means

Failure Cases and Mitigation Means

Types of risks are looked at and their consequences defined and mitigated. They are:

Total loss of the application
Server Corruption
Sent and filled function was lost

Mitigation means are processes and procedures defined to compensate each identified failure case. They are means to provide availability of the application and to ensure detection of a false output.

Table 3: Failure cases and Mitigation means in EForms module

FAILURE CASES	MITIGATION MEANS
Electronic forms do not syn-chronize to clients.	Existing eForms will be available and not deleted by the application. Logipad can work in offline mode. Digital form can be storage in PDF expert or paper forms as backup method
Electronic forms inputs are not imported into Logipad’s Server database.	Once eForms are sent to the server, eForms are cached an can be imported manually to the database at a later time.
Electronic forms cannot be filled and sent	Use spare spare device, or paper backup form. Logipad have offline functionality. Even during a connection loss (WIFI, eforms cannot be sent), eForms are stored in an out-box. Once the WIFI access is available Logipad will automatically resend the missing eForm(s).

GENERAL

TABLE OF CONTENTS

LIST OF TABLES

LIST OF FIGURES

LIST OF EFFECTIVE PAGES

LIST OF SIGNIFICANT CHANGES

PURPOSE OF MANUAL

ABBREVIATIONS

DEFINITIONS

MANAGEMENT AND ADMINISTRATION

EFB SYSTEM OVERVIEW/ CONTROL AND RESPONSIBLE:

LOGIPAD EFB SYSTEM

HARDWARE CONSIDERATION :

EFB MOUNTING DEVICES :

SOFTWARE/ EFB SYSTEM CONSIDERATION :

CONTROL AND RESPOSIBILITIES.

Management User Interface (MUI) Over view :

MUI Webservice/ Registration and login process;

General section :

Users/ Add Users :

Exporting and importing users :

Exporting users :

Importing users :

Content Roles :

Create a content role

Edit or delete a content role

Changing the user assignment to the role

Notification

Creating a notification

EFB Approval Process Guidance :

Flight manager - simple to use, control and export of flight data

Briefing section / management, and generate/ upload all flights by status

Import from PPS: Automatically import and generate multiple flights directly from Flight Planning system from API connection. The crews for multiple flights have been selected by creating and simply releasing the flights

Attachment Types: All attachment of the flights can be selected within briefing manager, Easy control and management

Definitions section: The section allows you can select, define and assign the layout ( Colour, Texts, Placement of content…) which you want apply for your package

Logipad Webclient

Logipad user interface :

Logipad Documents module :

Logipad Eforms Module :

Logipad App Center

Jasper report/ Logipad reporting server

Administration Folder

Access Group Memberships

Active Report Server

User reports :

Briefing Report Server :

Not finalized briefing :

Release Briefings :

Document Reports

All Documents Folder:

Confirmation by role:

Document report:

Documents by role:

LOGIPAD MODULES

OVERVIEW :

DOCUMENTATION MODULE :

Organize documents

Document templates

Create Folder

Publish a single document

Publisher multiple documents

BRIEFING MODULE :

User interface layout :

Logipad Navigation bar :

Briefing info and standards layout concept

Briefing Info

Flight Summary

Weather & NOTAMs

Flight Data

Additional Documents

Data Entry Field/ What need to know ?

Briefing package / Activated and transfer data during the flight

How to active a Briefing.

Role: Master User

Role: Non- Master Use

To Activate a Briefing as a Master User (Briefing icon with Crow icon)

How to active a Briefing as a non-Master User (briefing Icon without Crow)

Roll Back Briefing Activation

Real time Sync and Data exchanged

Force Failover Function/ Transfer role between devices for abnormal operation